Method and apparatus for sharing toll charges among several toll service subscribers

ABSTRACT

A method for apportioning a vehicular toll among toll service subscribers in a vehicle can include determining a number of occupants in the vehicle in order to determine a toll amount, and dividing the toll amount among the toll service subscribers in the vehicle. The method can also detect the number of occupants and/or toll service subscribers in the vehicle automatically, or by prompting toll service subscribers to enter the number of occupants.

CROSS REFERENCE

This application claims the benefit of, and is a divisional of, U.S.patent application Ser. No. 14/032,956, filed Sep. 20, 2013, which istitled the same as this application, the entirety of which is herebyincorporated by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to vehicular toll systems, andmore particularly to dividing toll charges among several entities usingthe same vehicle.

BACKGROUND

Tolls have long been used to fund the construction and maintenance ofroads. Such roads are often referred to as tollways. Traditionally allvehicles travelling on a road where tolls are charged had to stop attoll stations in toll plazas located along the tollway at intervals andpay a toll. Toll stations were either automated or manned, and requiredpayment in cash. Accordingly, payment of tolls required vehicles to stopand pay, causing congestion and delay at each toll plaza.

In recent years toll agencies have been increasingly using wirelesstechnology to automate toll payment and speed up the process toalleviate congestion at toll plazas. Wireless toll payment has developedto the point that vehicles can drive under a toll gantry at normalspeed, without having to slow down. As vehicles drive toward a tollgantry the vehicle is detected by the toll system and a reader for thelane in which the vehicle is travelling is activated, transmitting areader signal. A toll tag device in the vehicle receives and responds tothe reader signal, transmitting a tag identifier that is associated witha toll account to which payment is charged. The owner of the toll tagdevice is responsible for ensuring there are sufficient funds availablein the account. When a vehicle passes a toll gantry and fails to respondto the reader signal, a photo of the vehicle, taken as it passes thetoll gantry, can be processed to acquire a license number of thevehicle, and an infraction or citation can be issued to the registeredowner of the vehicle for payment.

The success of wireless, automated toll payment systems has alsorecently been used to generate revenue along roadways that are subjectto periodic congestion merely due to the volume of traffic at certaintimes by providing toll lanes alongside non-toll lanes of the roadway.Typically the toll lanes have very restricted access and limited exits,in part to prevent people from driving around toll gantries. Thus, thetoll lanes allow drivers a choice to bypass much of the congestion inthe non-toll lanes in exchange for payment of the toll. Some tollagencies adjust the toll amount based on the time of day or the amountof congestion in the non-toll lanes, increasing the toll at times whenthere is high congestion and reducing the toll when there is little tono congestion in the non-toll lanes.

Toll lane expressways alongside non-toll lanes are, in part, a responseto the problems of high occupancy vehicle (HOV) lanes. In manyjurisdictions, in an attempt to reduce congestion, HOV lanes have beenestablished for vehicles carrying more than one occupant. These lanestypically do not have restricted access, and while most people observethe HOV, solo drivers often take advantage of the relatively empty HOVlane rather than staying in the regular lanes, which tends to defeat thepurpose of the HOV, thus necessitating enforcement of HOV lanes.However, enforcement of HOV lanes typically requires officers patrollingthe HOV, often stopping offenders during peak traffic hours. Thepresence of law enforcement can aggravate congestion as offendersattempt to quickly change lanes and other drivers slow down upon seeinglaw enforcement vehicles patrolling HOV lanes, which further tends todefeat the purpose of HOV lanes.

Ideally, jurisdictions would like to encourage people to carpool or rideshare, as well as offer toll lanes for drivers willing to pay to avoidcongested lanes in a way that requires minimal enforcement activity.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed invention, and explainvarious principles and advantages of those embodiments.

FIG. 1 is a system diagram of a toll service system that supports tollsharing in accordance with some embodiments;

FIG. 2 is a toll system diagram showing a mobile device that enableswireless payment of tolls in accordance with some embodiments;

FIG. 3 is a flow chart diagram of a method for sharing toll charges inaccordance with some embodiments;

FIG. 4 is a flow chart diagram of a method for detecting a number ofsubscribers to share toll charges in accordance with some embodiments;

FIG. 5 is a flow chart diagram of a method for sharing tolls inaccordance with some embodiments;

FIG. 6 is a flow chart diagram of a method for providing travel timesavings information of a high occupancy toll lane in accordance withsome embodiments; and

FIG. 7 is a flow chart diagram of a method for generating a unique codedidentifier for use in a toll system that provides toll sharing inaccordance with some embodiments.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the present invention.

The apparatus and method components have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe present invention so as not to obscure the disclosure with detailsthat will be readily apparent to those of ordinary skill in the arthaving the benefit of the description herein.

DETAILED DESCRIPTION

The embodiments include a method of apportioning toll payment thatinvolves determining, at a toll service system, an identity of each of aplurality of toll service subscribers located together in a vehicle.Each toll service subscriber has a toll account with the toll servicesystem that is associated with each toll service subscriber,respectively. The method further includes receiving, at a toll servicesystem from one of the toll service subscribers, an indication of a tolltransaction occurrence. Responsive to receiving the indication of thetoll transaction occurrence, the toll service system debits the accountof each toll service subscriber in the vehicle for a portion of a tollamount for the toll transaction.

FIG. 1 is a system 100 for operating a toll service and a toll agency inaccordance with some embodiments. A toll agency refers to, typically, agovernmental organization that has established one or more toll roads ortoll lanes that can include toll plazas or toll stations, and collectstolls from vehicles, vehicle owners, or others operating vehicles foruse of the toll roads. A toll service refers to an organization thatmanages toll accounts for drivers and vehicle operators and owners, andinterfaces with the toll agency or agencies to ensure payment of tollscollected through automatic wireless toll stations. People can subscribeto the toll service and set up an account from which funds can bewithdrawn or debited to pay for tolls incurred by the account holderusing a vehicle or vehicles associated with the account.

Accordingly, a vehicle 101 can contain one or more toll servicesubscribers or subscriber devices 102, 103. As used herein, the termtoll service subscriber refers alternately either to a small, portablecomputing device that includes one or more radio transceivers or theperson who uses such a device and subscribes to a toll service,depending on the context. Examples of toll service subscribers include,for example, cellular or “smart” phones, tablet computing devices,personal digital assistants, and so on. In addition to radiointerface(s), a toll service subscriber 102 includes a graphical displayand input means to allow a user of the toll service subscriber 102 tointeract with, and control operation of the toll service subscriber 102,as well as memory and a processor to execute program code forapplications, programs, operating systems, and other software elements,such as, for example, a toll service application 118. The memoryincludes read only memory (ROM) and random access memory (RAM), and caninclude other types of memory such as flash memory, and can includememory expansion such as memory card slots. In some embodiments the tollservice subscriber 102 can be associated with an RFID tag device 104 toenable wireless toll transactions for payment of toll when the vehicle101 is travelling on tollways using wireless toll payment systems.

The RFID tag device 104 contains identity information that can be usedfor conducting wireless transactions. Accordingly, the RFID tag device104 includes at least two radio frequency (RF) interfaces. A RFinterface is a wireless radio interface and includes an antenna andtransceiver that operate according to a defined protocol or airinterface. The air interface defines channel format, timing, modulation,and other aspect for radio communication. The RFID tag device 104includes a first RF interface 107 to communicate with the toll servicesubscriber 102 via radio link 108, and a second RF interface 105 tocommunicate with another device, such as an RFID reader 110, over radiolink 112. The radio links 108, 112 indicate communication between thedevices over their respective RF interfaces. The RFID tag device 104 canbe held against, or substantially close to the toll service subscriber102, such as by forming the RFID tag device 104 in the form of a cardwith an adhesive layer to affix the RFID tag device 104 onto a surface(such as a back surface) of the toll service subscriber 102 as indicatedby arrows 106. In some embodiments the toll service subscriber 102 andRFID tag device 104 communicate via radio link 108 using a near fieldcommunication (NFC) protocol, such as that specified by theInternational Organization for Standardization (ISO) or InternationalElectrotechnical Commission standard (IEC) 18000-3 which has aneffective range of about 10 cm and operates at 13.56 MHz. Typically theNFC communication between the toll service subscriber 102 and the RFIDrag device 104 will be encrypted for security purposes. In addition toexchanging data over the radio link 108, the toll service subscriber 102can power the RFID tag device 104 via radio link 108. The energy of theNFC signal from the toll service subscriber can be collected in the RFIDtag device and used to by the RFID tag device 104 to respond to the tollservice subscriber over link 108, as well as for RFID operations viaradio link 112. Radio link 112 between the RFID tag device and RFIDreader 110 can be a RFID interface, such as, for example, that specifiedby ISO/IEC 18000-6C, ISO/IEC 18000-6B, the Interagency Group (IAG) TimeDivision Multiplexing (TDM) standard, or other known RFID interfacestandards. In some embodiments, the link 112 can be specificallyconfigured to operate according to a vehicular toll standard for use inwireless tollway systems. In such embodiments, the RFID reader 110 canbe a tollway reader that is positioned over a traffic lane of a tollroad. The RFID reader 110 includes an antenna and transceiver to supportcommunications with RFID tag devices, as is known. As the RFID tagdevice 104 passes by the reader 110, a signal from the reader 110 causesthe RFID tag device 104 to respond via link 112 with identificationinformation to identify the RFID tag device 104. Furthermore, the reader110 can, in some embodiments, transmit transaction information to theRFID tag device 104 via link 112. The transaction information caninclude information such as an identification of the reader 110,location, a toll amount, the time, and so on. In some embodiments thereader 110 does not transmit transaction information to the RFID tagdevice 104, and the RFID tag device 104 only indicates to the tollservice subscriber 102 that it has been read (i.e. that it has respondedto a reader signal).

The toll service subscriber 102 contains and executes a toll serviceapplication 118 that allows the toll service subscriber 102 tofacilitate toll transactions, including processing transactioninformation received from the RFID tag device 104 or transactioninformation generated by the toll service subscriber 102 upon receipt ofan indication of a transaction by the RFID tag device 104, andforwarding the transaction information to an account server 122. Thetoll service application 118 also enables toll sharing, allowing thetoll service subscriber to share toll payments with other toll servicesubscribers travelling in the same vehicle 101, such as toll servicesubscriber 103. By sharing tolls it is meant that each toll servicesubscriber 102, 103, is responsible for a portion of the toll, where thesum total of the respective toll portions paid by each toll servicesubscriber unit 102, 103 is equal to the toll amount.

In some embodiments the toll service subscriber 102 initializes the RFIDtag device 104 via link 108 before the RFID tag device 104 interactswith the RFID reader 110 via link 112. For example, in a vehicular tollembodiment, the toll service subscriber 102 can determine that the tollservice subscriber 102 is approaching a known toll gateway locationusing location information and road map data that indicates the locationof toll gateways. When the toll service subscriber 102, is within aselected distance of a toll gateway, the toll service subscriber 102 canenergize NFC link 108 to power up the RFID tag device 104. As the tollservice subscriber 102 and RFID tag device 104 pass through the tollgateway, the toll transaction occurs over link 112, and the RFID tagdevice 104 transmits transaction information to the toll servicesubscriber 102 via link 108. Any transaction information received at thetoll service subscriber 102 from the RFID tag device 104 can beprocessed by the toll service application 118, which can store thetransaction information as well as display the transaction informationupon receipt of the transaction information, or at a later time uponuser request. Once the RFID tag device 104 completes transmitting to thetoll service subscriber 102 subsequent to the transaction, the tollservice subscriber 102 can shut off the NFC link 108 to conserve batterylife of the toll service subscriber 102.

In some embodiments the toll service subscriber 102, in addition to theradio interface to support radio link 108, comprises another radiointerface to communicate at farther distances, such as a cellulartransceiver for communicating over a cellular radio telephony link 116with a cellular telephony infrastructure network 114. The cellular radiotelephony link 116 is operated in accordance with a cellular datacommunications standard, such as, for example, the Long Term Evolution(LTE) standard, the Global System for Mobile Communications (GSM)Enhanced Data rates for GSM Evolution (EDGE), or code division multipleaccess (CDMA), among other known standards. The toll service subscriber102 can transmit transaction information over the cellular telephonyradio link 116, through a wide area network 120, such as the Internet,to toll service 119 that includes one or more backend servers 121 andone or more account servers 122. The backend servers 121 provide tollservices as described herein, and the account servers maintain accountinformation for an account 123 associated with each toll servicesubscriber 102, 103. The account servers 122 can be linked to one ormore banks 124 to maintain funding for transactions applied to theaccount 123.

The toll service 119 can communicate with a back office server 128 of atoll agency that is associated with reader 110 over similar, if not thesame, networks 126, 130. The back office server 128 logs transactioninformation and reconciles payment of funds due with the toll service119. Processing the transaction information is typically performed bybatch processing, although in some embodiments it is contemplated thatprocessing can be performed on a per-transaction or per-occurrencebasis. The toll service 119 can verify transactions based on transactioninformation received from the toll service subscriber 102 using RFIDdevice 104. The toll service subscribers 102, 103, in some embodiments,can further include other radio interfaces such as, for example, awireless local area network (WLAN) interface, such as that described inthe Institute of Electrical and Electronic Engineers (IEEE) standard802.11 (a, b, g, n, etc.), and often referred to as “WiFi.” In someembodiments the toll service subscriber 102 can use the near fieldcommunication interface 108 to communicate with another device besidesthe RFID tag device 104, which can include a networked device that canforward transaction information from the toll service subscriber 102 tothe toll service 119 so that payment can be reconciled with the tollagency back office server 128 and debited to the account 123 inproportion to the respective toll service subscriber's portion of theshared toll.

It is contemplated that, in addition to sharing tolls, the toll servicesubscribers 102, 103 can provide the toll service 119 with occupantcount information indicating the number occupants in the vehicle 101(some occupants may not have toll service subscribers). In toll systemswhere a discount is given on the toll amount for vehicles with more thanone occupant, the toll service 119 can inform the toll agency, via backoffice service 128, for example, of the occupant count presentlyassociated with the identifier used by RFID tag device 104. In someembodiments the toll agency can maintain an account service 129 that issubstantially similar to account server 122, or instead of the tollservice maintaining account server 122. A toll agency-maintained accountserver 129 can manage accounts 131 for subscribers. Alternatively, thetoll service 119 can assert a discount upon settling toll transactionswith the toll agency. To prevent false occupant counts (e.g. relyingsolely on the user of the toll service subscriber 102), the toll service119 can make determinations to reduce the likelihood of false occupantcounts being used to obtain undeserved toll discounts. For example, thetoll service application 118 can report location information to the tollservice 119, which can then determine toll service subscribers 102, 103which appear to be co-located and moving together. In some embodimentsthe toll service application 118 can detect that it is in a vehicle,such as by monitoring its own location and determining that it is movingat a speed and along a roadway (using a map service, for example)indicative of vehicular travel, or by detecting the toll servicesubscriber 102 or 103 establishing a wireless personal area network(PAN) link with the vehicle (e.g using BlueTooth). To further discouragefalse occupant count information being provided to the toll service 119,a law enforcement application programming interface (API) can beprovided by the toll service 119 to allow law enforcement 125 todetermine how many occupants have been reported for a given vehicle.

FIG. 2 is a toll system diagram 200 showing a mobile device that enableswireless payment of tolls in accordance with some embodiments. A firstvehicle 202 travels in a toll lane 203 and carries one or more tollservice subscribers 204. Vehicles travel in the direction of arrow 206.A second vehicle 208 travels in a non-toll lane 209. The toll lane 203and non-toll lane 209 can be separated by a barrier, as is known, toprevent vehicles in the toll lane from switching into the non-toll lanebefore passing through a toll station 248, and likewise to preventvehicles in the non-toll lane from changing into the toll lane once pastthe toll station 248. The driver of the first vehicle 202 can decide todrive in the toll lane 203 to avoid traffic congestion in the non-tolllane 209. It will be appreciated that, although only one toll lane 203and non-toll lane 209 are illustrated here that there can be additionallanes of both types of lanes 203, 209.

The toll service subscriber 204 can include several components andsubsystems, such as a controller 210 that is coupled to a globalpositioning system (GPS) receiver 218, a cellular telephony radiotransceiver 212, and NFC transceiver 222, and memory 214. An tollservice application 216 can be stored in the memory that is executed bythe controller 210. The memory 214 can represent an aggregation ofdifferent types of memory, including ROM memory, RAM memory, bulkstorage memory, flash memory, and so on. The GPS receiver 218 canreceive GPS signals 242 transmitted by GPS satellites 240 to determinethe location of the GPS receiver 218 as is known. The toll serviceapplication 216 can request location information from the GPS receiver218 to compare the location of the GPS receiver 218 (and hence thelocation of the toll service subscriber 204). As the toll servicesubscriber 204 gets within a certain distance of the toll station 248,the toll service application 216 causes the toll service subscriber toturn on the NFC transceiver 222 so that it transmits to an NFC RFinterface 226 on the RFID tag device 224, thereby providing power(through the energy collector circuitry) to the RFID tag device 224.When the vehicle 202 then passes under the toll station 248, a tollreader signal is received by an RFID interface 228 of the RFID tagdevice 224, and the RFID tag device 224 responds to the reader signal bytransmitting the RFID information, including a substantially uniqueidentifier, to allow a toll charge to be debited to an account oraccounts associated with the identifier. Once the RFID tag device 224has been read by the toll station 248, an indication of the transaction,including transaction information, can be transmitted from the RFID tagdevice 224 to the toll service subscriber 204 via the NFC RF interface226.

The toll service subscriber can further include a wireless local areanetwork (WLAN) interface, often referred to as a WiFi interface 230 thatoperates according to a known WLAN protocol such as, for example, IEEEstandard 802.11 a, b, g, n, etc. The toll service subscriber 204 canfurther include a personal area network (PAN) interface 232, such as,for example, a BlueTooth interface. Additionally, or alternatively, thetoll service subscriber 204 can include an ultrasonic interface 234 forcommunicating using ultrasonic acoustic signals. The toll serviceapplication 216 can utilize the various interfaces 222, 230, 232, 234 tocommunicate with other nearby (e.g. in the same vehicle) toll servicesubscribers 236. Additionally, or alternatively, the toll serviceapplication can query the vehicle system 238 using the PAN interface232, for example. The vehicle system 238 can respond to the query withoccupant information determined, for example, using seat belt sensors orweight sensors in each seat. The occupant information can be stored atthe backend service of the toll service and accessed by law enforcementpersonnel using, for example, the law enforcement access 125 of FIG. 1.The toll service application 216 can also prompt 220 a user to enter anoccupant count in some embodiments. The toll service application 216 canreport the occupant count information to the toll service for tolldiscounts when using high occupancy toll (HOT) lanes (e.g. lane 203).Additionally, the toll service application 216 can receive informationfrom the toll service. The information can be received over a cellularnetwork 244 and can include, for example, expected travel time savings246 for using a toll lane compared to a non-toll lane for a section ofroad that the vehicle 202 is approaching, and the toll serviceapplication 216 can display or announce the received travel time savings246 to the user of the toll service subscriber 204.

FIG. 3 is a flow chart diagram of a method 300 for sharing toll chargesin accordance with some embodiments. At the start 302 one or more tollservice subscribers are powered on and located in a vehicle.Accordingly, the toll service subscribers can detect or determine thatthey are located in a vehicle in process 304, by, for example,determining movement indicative of vehicular travel, determining thatthe movement is along a roadway using GPS information and a mappingapplication, or by establishing a radio link to a vehicle system, or byreceiving a message from the toll service indicating that the tollservice subscriber appears to be moving in a vehicle. The method 300 canthen determine, in process 306, whether any toll service subscribershave selected or provided a subscriber and/or occupant count of theoccupants in the vehicle to the toll service system. If an occupantcount has been provided the method proceeds to process 308 to determinethe number of occupants. That is, a toll service application can attemptto verify the occupant count, such as by querying other toll servicesubscribers in the vehicle, and/or the vehicle system to determine thenumber of seats that are occupied in the vehicle. The method thenproceeds to process 310 where the method determines whether the numberof occupants provided matches the number detected. If yes, then themethod proceeds to process 320 where the method determines whether asubscriber has selected or authorized toll sharing. If so, then themethod proceeds to process 326 where the method charges toll amounts toeach participating subscriber in accordance with a prescribedproportion. The default proportion can be each subscriber pays an equalshare of the toll, but in some cases several of the occupants may bepaid for out of the same account, thus increasing the proportion of tollpaid by the corresponding account, such as when, for example, bothspouses car pool with other subscribers. The proportions can be userselectable in some embodiments. Returning to process 320, if tollsharing has not been selected, then the method proceeds to process 328where the method charges the toll to one subscriber.

Returning to process 310, the method can alternatively proceed fromprocess 310 to process 312 where the method determines whether thevehicle is approaching a HOT lane. If not, the method can proceed toprocess 328 and charge a single subscribe for non-HOT lane tolls.Alternatively, even non-HOT lane tolls can be shared by the subscribersin the vehicle using substantially the same processes. Returning toprocess 312, if the vehicle is approaching a HOT lane, the methodproceeds to process 314 where the toll service system gathers traveltime information for the HOT and non-HOT lanes and transmits anestimated travel time savings to the subscriber so that the subscribercan determine whether to enter the HOT lane or not. In process 316 themethod 300 determines whether the vehicle has entered the HOT lane. Ifso, the method 300 proceeds to process 318 and can provide a discountbased on the number of occupants, and then proceed to process 326,described previously. Returning to process 316, if the vehicle is not ina HOT lane, the method can proceed to process 328. It is contemplatedthat some tollways can charge a minimum toll in non-HOT lanes, and allowusers who car pool to receive a discount in HOT lanes.

Returning to process 306, if no subscriber has selected a number ofoccupants, the method 300 proceeds to process 322 where the method canprompt one or more subscribers to provide an occupant count of thenumber of occupants in the vehicle. Additionally, a proportion can beprovided as to how to apportion the toll charges to each subscriber inthe vehicle that is participating in the toll sharing. The method 300can then proceed to process 324, where the method 300 can receive thetoll sharing selection at the toll service system, which notes theselected sharing. Any discounts for using HOT lanes can also be applied.The method 300 then proceeds to process 326 to charge the subscribersaccording to the selected sharing. Finally, once the payment arrangementis decided, the method ends 330.

FIG. 4 is a flow chart diagram of a method 400 for detecting a number ofsubscribers to share toll charges in accordance with some embodiments.The method 400 can commence from the start 402 by determining thatseveral toll service subscribers are moving together in process 404. Thedetermination can be made by the toll service subscribers reporting tothe toll service system that they are moving. The method 400 can thenproceed to process 406 where the method determines if there is anability for the toll service subscribers to detect occupants in thevehicle (the number of occupants can be different than the number ofsubscribers). If not, the method proceeds to process 410 where themethod 400 sends a prompt from the toll service system to eachsubscriber in the vehicle to accept toll sharing, and they can indicatea sharing proportion. The method 400 then proceeds to process 430 wherethe method 400 splits toll charges among the subscribers according theselected proportion, or equally as a default. Returning to process 406,if there are occupant detection means available (e.g. querying thevehicle system, ultrasonic communication, local low power radiointerface, and so on) the method 400 can proceed to process 408 todetermine if there is any toll service subscriber paired with thevehicle system (e.g. using BlueTooth™). If so, then it can be assumed,in some embodiments, that the paired toll service subscriber is the mainaccount holder (412) and that the paired toll service subscriber will beassociated with an RFID tag device used to perform wireless tolltransactions and the method 400 proceeds to process 428. If, in process408, there are no subscribers paired to the vehicle system, the method400 can proceed to process 414 in an attempt to receive occupant countinformation from the vehicle (e.g. seat belt, seat weight sensors). Ifthe vehicle system can provide the information, then the method 400proceeds to process 434 and the seat information is used as the occupantcount. The method can optionally allow a user or subscriber to verifythe occupant count and toll sharing proportions in process 428. Themethod 400 then proceeds to process 430, where the toll charges aresplit accordingly.

Returning to process 414, if the vehicle system cannot provide seatsensor information, the method 400 can proceed to processed 416, 420,and 424, which are each different means for attempting to determine thenumber of subscribers in the vehicle. In process 416 the method 400attempts to use a NFC interface to detect other subscribers in thevehicle. In process 420 the method 400 attempts to use a WiFi interfaceto detect other subscribers in the vehicle. In process 424 the method400 attempts to use ultrasonic communication interface to detect othersubscribers in the vehicle. Processes 416, 420, 424 can be usedalternately, or in combination. If any of the processed 416, 420, 424can be used, they each can provide a count of other subscribers incorresponding processes 418, 422, 426. Once a count ofsubscriber/occupants is obtained the method 400 can optionally allow thecount to be verified or edited/adjusted in process 428. The method 400then proceeds to divide toll charges accordingly in process 430,whereupon the method 400 ends at process 432.

FIG. 5 is a flow chart diagram of a method 500 for sharing tolls inaccordance with some embodiments. From the start 502 the method 500proceeds to determine that the toll service subscriber is located in avehicle, which can be performed by the toll service application. Themethod 500 then determines if there is more than one toll servicesubscriber in the vehicle in process 506. If not, then the method merelyapportions the entire toll amount for toll charges to the one tollservice subscriber. If there is more than one toll service subscriberdetected in process 506, the method 500 can proceed to process 508 todetermine if the other toll service subscriber(s) are sub-accounts ofthe same account. If so, then in process 510 the main account is chargedfor all toll amounts. If not all of the detected toll servicesubscribers are sub-account holder, the method 500 proceeds to process514 to determine if there has been a selection of the number ofoccupants. If not, then in some embodiments the method 500 can proceedto process 532 to determine if the route being followed is a commonroute for one of the toll service subscribers. A common route is onewhich is frequently or regularly travelled by a subscriber. If so, thenin process 534 the method 500 can charge all toll amounts to the tollservice subscriber associated with the route. If several toll servicesubscribers share the common route, the toll amount can be split amongthem. If the route is not a common route, the method 500 can proceed toprocess 536 to determine whether any of the toll service subscribers arepaired with the vehicle system. If so, the method can proceed to process512 and charge the toll normally (e.g. to one subscriber). If there isno toll service subscriber paired with the vehicle system, the tollservice system can prompt each toll service subscriber to accept tollsharing, and allow the subscribers to provide toll sharing proportionsin process 538. The method 500 can then proceed to process 540 where themethod 500 can divide toll amounts accordingly.

Returning to process 514, if the number of occupants is selected ordetermined, the method 500 can proceed to process 516 to determine ifthe number of occupants selected matches with a number of occupantsdetermined to be in the vehicle (e.g. by performing method 400). If so,the method 500 proceeds to process 520 to determine if sharing has beenselected. If sharing has been selected, then in process 522 the tollservice subscribers are charged equally, or in proportion as indicated.If sharing has not been selected in process 520, then one subscriberaccount is charged for the full toll amount, such as the subscriber whoentered the number of occupants.

Returning to process 516, the method 500 can alternatively proceed toprocess 518 where the method 500 determines whether the vehicle isapproaching a HOT lane, or a tollway that has a HOT lane. If not, thenthe method 500 proceeds to process 524 and one subscriber is charged fortolls (or alternatively tolls are divided among subscribers in thevehicle). If the vehicle is approaching a HOT lane, the toll servicesystem can gather traffic information and determine a travel timesavings that can be achieved using the HOT lane instead of the non-HOTlanes. The method 500 can then determine if the vehicle is in the HOTlane in process 526. If so, then the number of occupants can be used todetermine a toll discount in process 530. If the vehicle is not in a HOTlane, then the method 500 can default to process 524.

FIG. 6 is a flow chart diagram of a method 600 for providing travel timesavings information of a high occupancy toll lane in accordance withsome embodiments. At the start 602, it has been determined that thevehicle is approaching a HOT lane, meaning that the vehicle is on a roadway that, farther down the roadway from where the vehicle is presentlylocated, a HOT lane begins. Thus, the method 600 provides travel timeinformation for the HOT and non-HOT lanes so the driver can determinewhich to use. Accordingly, in response to determining that the vehicleis approaching a HOT lane, the toll service system can gather trafficinformation for the HOT and non-HOT lanes ahead using, for example, dataacquired from WAZE, NAVTEQ, or traffic.com APIs in process 604. If thereis traffic information for the HOT lane in process 606, the method 600proceeds to process 608, where the toll service system can use a recentnumber (“X”) of traffic times of the non-HOT lanes (which can beadjacent the HOT lanes) and subtract them from the a recent HOT lanetravel time over the same distance. The method 600 can then proceed toprocess 610 to find the largest difference. In process 612 the method600 determines if there is a travel time savings. If there is no traveltime savings, the method 600 can proceed to process 616 and report thatthere is no time savings between the HOT and non-HOT lanes. If there isa significant different in travel time, as determined in process 612,then the method 600 can proceed to process 614 where the method 600reports the largest different in times and the potential maximum traveltime saving the driver may expect by using the HOT lane.

Returning to process 606, if there isn't commercial traffic reportingservice available, the method 600 proceeds to process 618 where themethod estimates velocity for the non-HOT lane based on reported traveltimes (which can be reported to the toll service system by other tollservice subscribers using the non-HOT lane) and the known distance. Inprocess 620 the travel time for the HOT lane can be estimated byassuming vehicles can travel at the speed limit of the HOT lane. Inprocess 622 the method 600 can subtract the reported or detected HOTlane estimated travel time from the travel times reported for thenon-HOT lanes, and the difference is reported to the toll servicesubscribers as the amount of time that can be potentially saved by usingthe HOT lane. Once the time savings (if any) is provided to the tollservice subscriber, the method 600 can then terminate 624.

FIG. 7 is a flow chart diagram of a method 700 for generating a uniquecoded identifier for use in a toll system that provides toll sharing inaccordance with some embodiments. In embodiments where a configurableRFID tag device is used, the toll service subscriber can configure theRFID tag device with a unique identifier that can be obtained from thetoll service system. At the start 702 a toll service subscriber candetermine that an identifier is needed. In process 704 the toll servicesystem can receive a request for an identifier from a toll servicesubscriber, including a count of the number of occupants in the vehicle.In process 706 the method 700 can generated a coded unique identifierthat is then associated with one or more subscriber accounts. The codedunique identifier can include coded information that indicates thenumber of occupants in the vehicle. In process 708 the toll servicesystem can transmit the coded unique identifier to the toll servicesubscriber. In process 710 the toll service subscriber can configure anassociated RFID tag device with the coded unique identifier, where, uponthe RFID tag device receiving a read signal when passing a toll station,the RFID tag device will respond with the coded unique identifier, whichis recorded by the toll agency for later toll settlement. The codedunique identifier can be decoded by the toll agency to determine thenumber of occupants in the vehicle and charge a corresponding discountedtoll. Once the RFID tag device is configured, the method 700 can thenterminate 712.

The embodiments described herein provide the benefit determining thenumber of occupants in a vehicle that is using a toll lane, as well asthe ability to split the toll amount among the occupants or subscribersin the vehicle. In some embodiments the toll is not split, but rathercharged to a single toll service subscriber account, although the tollamount can be discounted based on the number of occupants in thevehicle. This allows roadway authorities who operate a toll agency theability to reward high occupancy vehicles with toll discounts (includinga total exemption), and it allows travelers the ability to reduce theamount of toll they each pay by apportioning the toll amount(s) amongseveral others. In some embodiments the detection of other toll servicesubscribers and occupants in the vehicle can be automatic, and in someembodiments the detection can involve a manual process where one or moretoll service subscriber users enter the number of occupants into theirrespective toll service subscriber or subscriber device for transmissionto the toll service system.

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the invention as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The invention is definedsolely by the appended claims including any amendments made during thependency of this application and all equivalents of those claims asissued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has”,“having,” “includes”, “including,” “contains”, “containing” or any othervariation thereof, are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises, has,includes, contains a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus. An element proceeded by“comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . .a” does not, without more constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises, has, includes, contains the element. The terms“a” and “an” are defined as one or more unless explicitly statedotherwise herein. The terms “substantially”, “essentially”,“approximately”, “about” or any other version thereof, are defined asbeing close to as understood by one of ordinary skill in the art, and inone non-limiting embodiment the term is defined to be within 10%, inanother embodiment within 5%, in another embodiment within 1% and inanother embodiment within 0.5%. The term “coupled” as used herein isdefined as connected, although not necessarily directly and notnecessarily mechanically. A device or structure that is “configured” ina certain way is configured in at least that way, but may also beconfigured in ways that are not listed.

It will be appreciated that some embodiments may be comprised of one ormore generic or specialized processors (or “processing devices”) such asmicroprocessors, digital signal processors, customized processors andfield programmable gate arrays (FPGAs) and unique stored programinstructions (including both software and firmware) that control the oneor more processors to implement, in conjunction with certainnon-processor circuits, some, most, or all of the functions of themethod and/or apparatus described herein. Alternatively, some or allfunctions could be implemented by a state machine that has no storedprogram instructions, or in one or more application specific integratedcircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic. Of course, acombination of the two approaches could be used.

Moreover, an embodiment can be implemented as a computer-readablestorage medium having computer readable code stored thereon forprogramming a computer (e.g., comprising a processor) to perform amethod as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, a CD-ROM, an optical storage device, a magnetic storagedevice, a ROM (Read Only Memory), a PROM (Programmable Read OnlyMemory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM(Electrically Erasable Programmable Read Only Memory) and a Flashmemory. Further, it is expected that one of ordinary skill,notwithstanding possibly significant effort and many design choicesmotivated by, for example, available time, current technology, andeconomic considerations, when guided by the concepts and principlesdisclosed herein will be readily capable of generating such softwareinstructions and programs and ICs with minimal experimentation.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

We claim:
 1. A method of apportioning toll payment, comprising:receiving, at a server of a toll service system, location informationfrom each one of a plurality subscriber devices, the locationinformation of each one of the plurality of subscriber devices includinga plurality of location coordinates produced over a time period by therespective one of the plurality of subscriber device; comparing, by theserver of the toll service system, the location information receivedfrom the plurality of subscriber devices; identifying, by server of thetoll service system, responsive to the comparing step, ones of theplurality of subscriber devices that have a common location at a commontime, and have a common direction as being located together in avehicle; determining, at the server of the toll service system, aplurality of identifiers, each one of the plurality of identifiersbelonging to a respective one of the plurality of toll servicesubscriber devices that are located together, each toll servicesubscriber device being associated with a respective one of a pluralityof toll accounts of the toll service system; configuring one of theplurality toll service subscriber devices to act as a toll tag device tobe read by a toll agency tag reader upon the vehicle passing by the tollagency tag reader; generating, by the server of the toll service system,a unique tolling identifier in response to determining the identity ofeach one of the plurality of toll service subscriber devices and theserver of the toll service system associating each of the plurality oftoll accounts with the unique tolling identifier, wherein the uniqueidentifier is coded, and when decoded indicates the number of to servicesubscriber devices in the vehicle; transmitting the unique tollingidentifier from the server of the toll service system to the tollservice subscriber device that is configured to act as the toll tagdevice, and wherein the unique tolling identifier is valid while thetoll service subscriber devices remain located together or for a periodof time; upon the vehicle passing by the toll agency tag reader, thetoll service subscriber device that is configured to act as the toll tagdevice transmitting the unique identifier to the toll agency tag reader;a server of the toll agency decoding the unique identifier transmittedby the toll service subscriber device and in response, determining atoll amount based on the number of toll service subscribers indicated bythe unique identifier, receiving, at a toll service system from one ofthe toll service subscriber devices, an indication of a toll transactionoccurrence including the unique tolling identifier; and responsive toreceiving the indication of the toll transaction occurrence, the serverof the toll service system debiting each one of the plurality of tollaccounts a portion of the toll amount for the toll transaction.
 2. Themethod of claim 1, wherein determining the identity of toll servicesubscribers located together in the vehicle comprises receiving, at thetoll service system, from one of the toll service subscribers, anidentifier of each of the other toll service subscribers.
 3. The methodof claim 1, further comprising verifying, by the toll service system,that the toll service subscribers agree to share toll charges.
 4. Themethod of claim 3, wherein verifying that the toll service subscribersagree to share toll charges comprises the toll service system queryingeach of the toll service subscribers and receiving an affirmativeresponse to the query.
 5. The method of claim 1, further comprisinggenerating the unique identifier by the toll service system based inpart on a number of occupants of the vehicle.
 6. The method of claim 5,further comprising one of the toll service subscribers determining thenumber of occupants at least in part automatically by at least one of:using a near field communication protocol to communicate with at leastone other of the toll service subscribers, using a wireless local areanetwork to communicate with at least one other of the toll servicesubscribers, using an ultrasonic communication protocol to communicatewith at least one other of the toll service subscribers or communicatingwith the vehicle to receive a count of occupied seats in the vehicle. 7.The method of claim 5, further comprising, receiving at the toll servicesystem the number of occupants of the vehicle prior to providing theunique identifier.
 8. The method of claim 5, further comprisingdiscounting the toll amount based on the number of occupants of thevehicle.
 9. The method of claim 1, further comprising: determining thatthe vehicle is traveling on a roadway having both a toll lane and anon-toll lane; and providing, by the toll service system to at least oneof the toll service subscribers, an indication of a travel timedifference between the toll lane and the non-toll lane.
 10. The methodof claim 1, wherein determining the identity of each of the toll servicesubscribers comprises receiving from one of the toll service subscriberdevice a list identifying the toll service subscriber.
 11. The method ofclaim 1, further comprises receiving from at least one of the tollservice subscribers at the toll service system a debiting proportionindicating a corresponding proportion of the toll amount to be debitedto each of the toll service subscriber accounts; and wherein debitingeach toll service subscriber account comprises debiting each tollservice subscriber account according to the corresponding proportion.